VMware KB: Running data collection on a new VMware vRealize Orchestrator endpoint in VMware vRealize Automation fails with the error: Full authentication is required to access this resource.
This KB article is just one more indicator that you should use lower case for names and addresses for the components of vRealize Automation. I have spent more time than with customers troubleshooting issues related to mixed case host names, dns records, etc.
Do yourself a favor: standardize on lowercase names!
VMware KB: Error when uploading files to vCenter Server Appliance using WinSCP.
This KB article describes how to set the default shell for “root” to bash to facilitate file operations on vCenter 6.x virtual appliances.
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: NSX for vSphere 6.1.3 is compatible with vSphere 6.0, but new vSphere 6.0 features have not been tested with NSX.
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: Creating an NSX logical switch fails with the error: Unable to allocate an available resource.
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.