Parking this here for later reference in class.
I am troubleshooting a DHCP relay issue with the DLR and have found this KB article useful in identifying known issues with NSX 6.x for vSphere. The article get updated periodically.
It turns out we ran across a bug that should be fixed with version 6.2.3.
This is an old KB that still gets referenced when odd things happen with new Windows VMs.
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!
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
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.
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.