The topics “How do I get root access to the different NSX components” or “How can I find the root password” comes up quite often. For some components it’s already widely documented (for example NSX Manager) and for other components it’s rarely described (for example the NSX controllers). I also haven’t yet found a complete overview of how to get root access to the underlying Linux layer on all components. So I thought I’d put this information together here for the NSX versions 6.3 and 6.4.
vCloud Director has been adding an Auto Discovery feature for VMs in version 8.20 and it’s available for some time now. It’s a cool feature that can simplify migrations, but in practice there are some pitfalls that can make things difficult. To be more concrete: It only works under certain conditions. Tom Fojta has written an article about this feature some time ago (Thanks, Tom). But I think some details are missing and that inspired me to post this.
By default, vCloud Director does not limit the size of memory, disks and number of vCPUs when creating a new virtual machine. This means the global configuration maximums for vSphere apply, which can be a problem for a service provider. Depending on the settings in the allocation model that a SP uses.
If you have already worked with IPv6 Default Routes in NSX 6.3, you may know the following problems: You set a static default route to ::/0, save your change and when you reload the page, the change is gone.
Or you want to upgrade the NSX Edge Gateways from version 6.2.x to 6.3.x and the Edge upgrade fails with an IPv6 error message.